System for integrating security and access for facilities and information systems

ABSTRACT

A system for integrating security and access for facilities and information systems is provided including a computer server, information systems, and facility protection systems. The information systems and facility protection systems are coupled for communication to the computer server via a network. Facility protection systems represent an access control system for controlling entry/exit to areas of buildings, such as with badges or other ID Credentials and other systems, such as intrusion detection and fire systems, to provide protection in facility environments. Information systems each represent a computer system requiring user authorization, via computers or terminals capable of connecting thereto, to access information resources or network environments protected by the computer system. Information systems may also include information protection systems requiring user authorization for external access to other information systems. The computer server has a central database which stores at least information defining users and their access privileges to the information systems and to areas of facilities controlled by access control system. Each of the information systems and facility protection systems sends event data to the computer server when an event occurs on its respective system, and an event transaction processor in the computer server determines action(s), if any, to take in response to one or more received events and accordingly sends action data to other information systems and facility protection systems to instruct such systems to automatically respond to security risks representing by such events in real-time. Central management of users and their access privileges, and monitoring of events is further provided.

This application is a continuation of U.S. patent application Ser. No.09/906,554, filed Jul. 16, 2001 now U.S. Pat. No. 7,380,279.

FIELD OF THE INVENTION

The present invention relates to a system (and method) for integratingsecurity and access to facilities and information systems, and relatesparticularly to a system for integrating security in the facilitiesphysical environment provided by facility protection systems withsecurity access to data and network environments provided by informationsystems. Facility protection systems may represent an access controlsystem for controlling entry/exit to areas of buildings, fire system,and intrusion detection system, or other physical environment protectionsystems, such as digital video recording and surveillance system,building automation system, or personal alarm safety system. Informationsystems each represent a computer system, requiring user authorizationvia computers, terminals or other computer-based devices, incommunication thereto, to access the information resources and networkenvironments protected by the computer system. Information systems mayalso include information protection systems requiring user authorizationfor external access to other information systems. The invention isuseful for enabling events occurring at a facility protection system orinformation system that may pose a security risk to automatically causeactions, in accordance with such events, in other facility protectionsystems or information systems, such that the security risk may beresponded to automatically and in real-time in both the facilitiesphysical environment, and the data and network environments protected byinformation systems. In addition, the invention is useful for centralmanagement of users and their access privileges and integratedmonitoring of events at facility protection systems and informationsystems.

BACKGROUND OF THE INVENTION

Conventionally, electronic access control to areas of buildings involveaccess controllers coupled to readers and similar devices which controllocking mechanisms to doors accessing areas of buildings. Accessdecisions, responsive to a badge or other user identifying means read bysuch readers, are based on information stored in a central computerdatabase or in local databases of the access controllers. Suchfacilities access control systems are described for example in U.S. Pat.Nos. 4,839,640 and 4,218,690, and also the ONGUARD® systems sold byLenel Systems International, Inc., Rochester, N.Y. Events detected byaccess control systems indicating that security has been compromised canbe monitored by security personnel, but are not capable of automaticallyaffecting user access in information systems, such as Windows NT,Windows 2000 or Unix servers, which often have terminals or computerslocated in the same physical environment controlled by the facility'saccess control systems. Typically, access to information is provided byuser authorization, such as Login ID and associated password maintainedby a system administrator. As a result, a user whose access privilegesto areas of a building have been discontinued, often continues to haveaccess to sensitive data maintained on information systems for a periodof time, i.e., until a system administrator for the information systemsis notified and then updates the user's access to the informationsystems, such as by disabling their Login IDs and passwords.

Similarly, at an information system, a user whose access, such as byLogin ID and password, may have been blocked, can often continue tohaving access to areas of a building for a period of time, i.e., untilan administrator of the facility's access control system is notified andthen changes the user's privileges to access such areas. The delaybetween the blocking of access to an information system or facilitiesaccess control system after a security breach is detected may beminutes, hours or days, depending on the responsiveness of personnel andeffectiveness of company policy and procedures. Such a delay can bedetrimental to the ability of a company, government organization, orother institution, to protect sensitive information. Further, oftenother types of facility protection systems are provided in the sameenvironment as the access control system, including digital videosurveillance, fire and intrusion detection (burglar) systems, which maydetect events posing risk to a facility, personnel, and informationsystems. Such events, although reported to security personnel monitoringfacility protection systems, do not necessarily cause any automaticactions to protect data maintained by the information system, or in thecase of intrusion detection (break-in), limit door exits by the accesscontrol system in the area of the detected intrusion.

Accordingly, it would be desirable to provide integrated monitoring andreal-time response to events occurring in facilities physicalenvironment protected by facility protection systems (such as accesscontrol systems, fire and intrusion detection systems) and data andnetwork environments of information systems, respectively, such thatevents occurring in facility protection systems can cause actions atinformation systems to protect access to data and networks, and eventsoccurring at information systems can cause actions at facility systemsto protect facilities controlled/monitored by such facility protectionsystems. Furthermore, it would also be desirable to integrate themanagement of users and their access privileges to the facilityenvironment controlled by a facility's access control system with userand access privileges to the data and network environments controlled byinformation systems.

Complex login procedures have been developed for information systems toincrease secure access to such systems, such as described, for example,in U.S. Pat. Nos. 6,035,405, 5,887,140, 5,892,901, 5,970,227, and5,712,973. Such login procedures have involved the use of other loginmeans, such as biometric, fingerprint, smart cards, security tokens orbadge ID information, often with authorization circuitry coupled toterminals of information systems enabling reading of such information.However, such information systems do not link access to informationsystems with access to facilities, in which the management of users andaccess privileges to facilities and information system are integrated ina single system.

SUMMARY OF THE INVENTION

Accordingly, the principal object of the present invention is to providea system and method for integrating security and access to facilitiesand information systems.

An object of the present invention is to provide a system forintegrating security and access to facilities and information systems inwhich events detected by facility protection systems can automaticallycause actions at information systems, and vice versa, in real-time.

Another object of the present invention is to provide a system andmethod for integrating security and access to facilities controlled ormonitored by facility protection systems with security and access toinformation systems by linking such systems using a computer servercapable of responding to events at such systems and integratingmanagement or user and access privileges to such systems.

A further object of the present invention is to provide a system forintegrating security and access for facilities and information systemsthat provides integrated, centralized monitoring for events generated byfacility protection systems and information systems.

Briefly described, the present invention embodies a system including acomputer server system, referred to herein as the security server,facility protection systems and information systems, where the facilityprotection systems and information systems are coupled to the securityserver by a data communication network. Facility protection systemsrepresent an access control system for controlling entry/exit to areasof buildings, and one or more other systems, such as fire system,intrusion detection (burglar) system, and digital video recordingsystem. Information systems each represent a computer system, such as acomputer server (e.g., Windows NT, or Unix servers) requiring userauthorization via computers, terminals or other computer-based devicescapable of communication to the computer system, to access theinformation resources (e.g., databases) and network environmentsprotected by the computer system. Information systems may also includeexternal access protection system (e.g. firewall or Virtual PrivateNetwork) requiring user authorization to enable external access to otherinformation systems that protect information resources and networkenvironments, such as described above. User authorization may refer toany authorization means, such as smart cards, biometrics (e.g. face,retina, or fingerprint recognition), security tokens and PIN, or LoginID and password, to access the data and network environments maintainedby information systems. The security server has a central database thatstores at least information defining users (user data), their accessprivileges to entry/exit to areas of buildings by the access controlsystem, and their access privileges to the information systems. Thecentral database may also store information defining the users' accessprivileges for masking of zones monitored by the intrusion detectionsystem. Each of the information systems and facility protection systemssends event data packets to the security server when an event occurs ontheir respective system with information about the event. The securityserver stores received events chronologically in an event log in thecentral database, and an event transaction processor in the securityserver determines the action(s), if any, to take in response to thereceived event data packets. When an event from one of the facilityprotection systems is received and action is required, action datapackets are sent by the security server to information systems and/orone or more other facility protection systems instructing them to takean action in accordance with the event. Similarly, when an event from aninformation system is received and action is required, an action datapacket is sent by the security server to one or more facility protectionsystems, or other information systems, instructing them to take anaction in accordance with the event. The security server formats eachaction data packet to include a command in accordance with theinstruction set of respective system to receive the action data packet.Each of the information systems and facility protection systems may havean interface (hardware and software) which directs their respectivesystem to respond to commands of received action data packets, therebyinstructing such systems to automatically respond in real-time to eventsreceived by the security server. The interface further collects eventsoccurring at their respective system and formats such events in one ormore event data packets for transmission to the security server andstorage in the event log in the central database.

The security server provides for download of user data, includingsecurity information (e.g., access privilege information), from thecentral database to the access control system, when such user dataaffecting security is changed (added, deleted, or revised) in thecentral database. The security server further updates access privilegesto information systems when user data affecting security is changed(added, deleted, or revised) in the central database. Such changes maybe made as a result of changes in an external database or repositorysuch as maintained by a human resources (HR) department of anorganization, in which changes in the external database are mapped bythe security server to records of tables stored in the central databasefor such user data. Based on such user data received from the externaldatabase, the security server determines the access privileges forfacility protection systems which control access (the access controlsystem access—entry/exit to areas of buildings, and/or the intrusiondetection system—masking of monitored zones), and access privileges forinformation systems. The central database may be reviewed and changed byone or more administration computer systems (clients) in datacommunication with the security server, via the network or other networkor connection, such as to integrate management of users and their IDCredentials (such as badges, smart cards, tokens, biometric information,login ID, or passwords) needed to access protected facilities andinformation systems. Events, especially events representing alarms(potential security risks), received by the security server are providedto one or more alarm monitoring systems (clients) in data communicationwith the security server, via the network or other network orconnection, thereby integrating monitoring of events at facilityprotection systems and information systems.

Although facility protection systems are described as access control,fire, intrusion detection, and digital video recording systems, they mayinclude other types of systems, such as a building automation system,intercom system, personal safety alarm systems, or asset tracking andmanagement systems, or other systems typically used for protection andmanagement of personnel and property in facilities environments.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing objects, features and advantages of the invention willbecome more apparent from a reading of the following description inconnection with the accompanying drawings, in which:

FIG. 1 is a block diagram of the system according to the presentinvention showing a computer server (security server) coupled by anetwork to facility protection systems and information systems;

FIG. 2 is a block diagram of the system of FIG. 1 showing the processingof an event from a facility protection system, the access controlsystem, to cause actions at information systems;

FIG. 3 is a block diagram of the system of FIG. 1 showing the processingof an event from an information system to cause actions at the accesscontrol system;

FIGS. 4A and 4B are connected flow charts showing the process in thesystem of FIG. 1 for downloading security information to the centraldatabase and distribution of security information to access controlsystem, intrusion detection system, and information systems;

FIGS. 5A and 5B are connected flow charts showing the process in thesystem of FIG. 1 when an event occurs at the access control system;

FIGS. 6A, 6B and 6C are connected flow charts showing the process in thesystem of FIG. 1 when an event occurs at an information system; and

FIG. 7 is flow chart showing the operation of the event transactionprocessor in the security server of the system of FIG. 1.

DETAILED DESCRIPTION OF INVENTION

Referring to FIG. 1, a system 10 is shown having a computer serversystem referred to herein as the security server 12, with memory storinga central database 14. The security server 12 represents a networkcapable computer system, and memory storing central database 14 may be ahard disk drive, or a separate memory storage unit coupled to thesecurity server 12. The security server 12 is connected to facilityprotection systems 22 and information systems 18, via a network 20, inwhich systems 18 and 22, and security server 12, each have an interface(hardware and software) enabling network communication. Network 20represents any typical computer network, such as LAN, WAN, or Internet,in which each component in the network has an IP address. Data may besent through the network 20 in packets, or files, to components by theirIP address, as typical of network communication protocol. Although lesspreferred, one or more components in system 10 may be serially connectedto communication ports on security server 12 in which a typical serialcommunication protocol is used. As will be described, security server 12receives event data from systems 18 and 22, logs them in the centraldatabase 14, routes events to alarm monitoring clients and to the eventtransaction processor and then, depending on the event data, outputsaction data packets (requests) to such systems 18 and 22, different fromthe system from which the event data is received, to take specificactions automatically and in real-time. The security server 12 may sendin response to event data, messages to one or more output devices 16,such as automated calls to pagers, telephones, or e-mail, or othercommunication systems. Output devices 16 include the appropriateinterfaces to such communication systems for such systems to operate inaccordance with phone numbers or e-mail addresses.

Facility protection systems 22 include an access control system (ACS) 22a, intrusion detection or burglar system (IDS) 22 b, fire system 22 c,and digital video recording and surveillance systems 22 d. The accesscontrol system 22 a is described in U.S. patent application Ser. No.09/135,822, filed Aug. 18, 1998, which is incorporated herein byreference, and assigned to the same assignee as the present application.The computer server described in this patent application may providesecurity server 12 with central database 14, and is further programmedas described herein to provide an integrated security system 10 forfacility protection systems 22 and information systems 18. In brief, theaccess control system 22 a includes one or more access controllers inwhich each access controller is coupled to one or more card readers.Each access controller may be separately connected to network 20 forcommunication with security server 12. The card readers read data frombadges and any pin number data entered at a keypad of the reader. Theaccess controllers each make access decisions responsive to data fromthe card reader for controlling locking mechanisms to doors accessingareas of buildings. For example, the access control system 22 a may bethe ONGUARD® system sold by Lenel Systems International, Inc. ofRochester, N.Y. However, other types of access control systems may alsobe used capable of communication with security server 12.

Intrusion detection system 22 b represents a system for detectingbreak-ins in a facility, such as with sensors detecting motion,window/glass breakage, and the like. The intrusion detection system 22 boperates such sensors in multiple zones of a facility, as typical ofintrusion detection systems. One or more IDS panels and alarm keypadsare present in the facility capable of controlling operation of thesystem 22 b in specific or multiple zones. The panels each have aninterface coupling the panel to the security server 12 via network 20,or a single interface may be provided to all or groups of panels. Withthe proper code entered on the alarm keypad one or more zones may bemasked to avoid sensor(s) in such zones from triggering an alarm eventin system 22 b. These codes may be an ID associated with the user insystem 10. For example, intrusion detection system 22 b may be a systemsuch as manufactured by Digital Monitoring Products, Inc. ofSpringfield, Mo.

Fire system 22 c represents a life safety system providing firedetection used in facilities, such as with sensors for detecting smokeor heat, and the like. The systems may incorporate visual or audioalert, and control sprinklers, if present in a facility. Such systemshave fire panels in the facility capable of controlling operation ofsystem 22 c. The panels each have an interface coupling the panel to thesecurity server 12 via network 20, or a single interface may be providedto all or groups of panels. For example, fire system 22 c may be asystem such as manufactured by Pyrotronics, Inc. of Cedar Knolls, N.Y.

Digital video recording and surveillance system 22 d representssurveillance system of digital video cameras connected to video serversor IP based digital video cameras located in areas of facilities. Eachsuch IP camera may have a network interface to connect directly tonetwork 20. These cameras are capable of detecting motion within theirviewing area by detecting changes between two bitmap images or videoframes successively taken by the camera. The cameras may be activated inresponse to signals (commands) from security server 12 to take stillpictures or full motion video of a scene to record it to video server,or download images or video directly to the security server 12 formonitoring and storage in central database 14.

Facility protection systems 22 may include other systems, such as anintercom system, personal safety alarm systems, physical assetmanagement systems, building automation system, or other systemstypically used for protection and management of personnel and propertyin facility environments. The intercom system utilizes intercoms atdoors in a facility, such as, for example, the Alphacom systemmanufactured by Stentofon, Inc. Personal safety alarm systems representhandheld or worn portable transmitters that can transmit an alarm signalwhen activated by a user indicating the location, transmitter, user nameor other identifier, and the time and date. Personal safety alarmsystems are manufactured, for example, by Viasonic, Inc. Physical assetmanagement systems provide for tracking and recording asset movement ina facility. Such systems use active or passive RF tags on assets, suchas business equipment, which may be read by sensors in a facility toindicate location and movement of assets. Asset management systems, forexample, may track passive RF tags, such as used in the Proxtrack Systemmanufactured by HID, Inc. and IBM, Inc., as described in Asset IDProgramming Specification, Version 1.1, published by IBM PersonalSystems Group, Feb. 5, 1999, and Asset ID RF Signal and ProtocolSpecification, Version 1.0, published by Atmel Corporation, HIDCorporation, and IBM Corporation, Nov. 3, 1998. Active RF tags aremanufactured by Automatic Identification Technology. Building automationsystems are systems providing control of heating, temperature, airconditioning, lighting, or energy flow in a facility, such asmanufactured by Honeywell, Inc., Johnson Controls, Inc., or AutomaticLogic, Inc. The digital video management and surveillance system 22 dand asset management system may be part of the OnGuard® System, asdescribed in Lenel OnGuard Technical Functional Generic Specification,published by Lenel, Inc., June 2000.

Each facility protection system's interface is capable of datacommunication with the security server 12 over the network 20, such thatevents occurring at such system are sent to the server for processing.These interfaces and their communication protocol are set forth by themanufacturer of their system to enable compatible communication withsecurity server 12. For example, typically the Bac Net or EchelonProtocol is used for interfacing with building automation systems.Certain components of the facility protection systems 22 may also beable to take actions in response to commands from the security server12, such as the assess control system 22 a, intrusion detection system22 b, fire system 22 c, and digital video recording and surveillancesystem 22 d, as will be described later in more detail.

The information systems 18 represents typical data network systems, suchas Windows NT Server 18 a, Lightweight Directory Access Protocol (LDAP)Server 18 b, or Unix/Linux Server 18 e, and information protectionsystems, such as firewall system 18 c or Virtual Private Network (VPN)system 18 d. Servers 18 a, 18 b, 18 d and 18 e may be located in areasof buildings controlled by the access control system 22 a, or monitoredby other facility protection systems 22, and are coupled to terminals,personal computers, or work stations, which also may be in other areasof such buildings. Firewall system 18 c is an information systemenabling outside (external) access, such as dial in through a PublicSwitched Telephone Network (PSTN), to users from external computers toaccess information resources, such as other information systems 18,located on network 20. Each information system 18 provides userauthorization through Login ID and associated passwords, security tokenand PIN, or smart card and digital certificates, to enable access byusers through a login screen. Other user authorization means may also beused, such as biometric fingerprint, voice and face data. One or more ofthe information systems 18 may be present in system 10. Informationsystems 18 are not limited to those shown in FIG. 1, and any type ofcomputer or network-based information system could be used whichrequires user authorization to access to network and data resources, andis capable of communication with security server 12, such as non-LDAPdirectory servers, network switches, network routers, SNMP controllabledevices, PKI Systems, or digital certificate authorities. Networkoperating systems other than Windows NT Server 18 a or Unix/Linux Servermay also be represented by information systems 18, such as Windows 2000Server. Other systems than firewall 18 c and VPN 18 d systems may alsobe used to provide external access protection before allowing access toa user authorization screen (e.g., login screen) for another informationsystem, such as servers 18 a or 18 e.

Each of the information systems' interfaces, like that of the facilityprotection systems, is capable of receiving and sending data packets(records or files) to and from security server 12 via network 20. Eachinterface of systems 18 and 22 receives action data packets directed tothe assigned IP address of systems 18 and 22, or a component thereof.The interface interprets and formats the commands and data of eachaction data packet for controller(s) in the system receiving the actiondata packet. Each controller in systems 18 and 22 operates in responseto the interpreted commands to effect an action. For example, actiondata packets may be directed to one of information systems 18, accesscontrol system 22 a, or intrusion detection system 22 b to cause changesin users' security access to their respective system. For informationsystems 18, the controller coupled to the interface may be composed ofsoftware modules that control user authorization, e.g., user login andpassword, access control list, security policies or accounts, orresources definitions. For access control system 22 a, the interfacerepresents a software access control driver coupled to one or morehardware access controllers, as described in the earlier incorporatedpatent application, in which such controllers make access controldecisions.

The commands used by the security server 12 in action data packetsdepend on the Application Programming Interface (API) or interfaceprotocol, for the particular one of systems 18 or 22, or componentthereof, to which such action data packet is being sent, as defined bythe manufacturer of the system in reference manuals for their interface.For example, one or more of the information systems 18, such as WindowsNT Server 18 a, have a defined API, as described in Microsoft Win32 APIProgrammers Reference, published by Microsoft, Inc. For example, accesscontrol system 22 a interface may be in accordance with Lenel OpenDeviceAPI, published by Lenel Systems International, Inc. Interfacing withintrusion detection system 22 b may be described, for example, in theD6600 Communications Receiver/Gateway Computer Interface Manual, whichis published by Radionics, Inc., and which utilizes the “SIA Format”Protocol Digital Communications Standard for Alarm SystemCommunications, published by the Security Industry Association.Interfacing with fire system 22 c may be described for example inCereberus Pryontronics Programmers Reference Manual, published byCereberus Pyrotronics, Inc.

The security server 12 has software for mapping actions to be taken intocommands in communication protocol for the interface for each facilityprotection system 22 and information system 18, such that the interfacecan interpret the command and data content, or fields, in an action datapacket for it's respective controller(s). To facilitate this, thesecurity server 12 may employ an agent software program that providessuch mapping of a set of functions (actions) to the instruction set of aparticular component in systems 18 and 22.

Each interface of the information systems 18 and facility protectionsystems 22 is programmed to also collect events occurring at itsrespective system. Such events may be sent from the controller(s) ofaccess control system 22 a and information systems 18 into memoryallocated in such systems for storage of events. The interface sendsdata representing one or more collected events in one or more event datapackets to the security server 12. The event data packets include aunique System ID, so that from data packets sent to the security server12, the originator (sender) of the event data packet can be identified.Each addressable part, i.e., controller, interface, or device, of theinformation systems 18 and facility protection systems 22 may have aunique System ID in system 10. The System ID may be a single identifieror composed of several identifiers that indicate levels of subcomponentsin a system.

For information systems 18, typical events would be the logon of a user(an authorization event), logoff of a user, failed user attempt tologon, or change in user password or access privilege of the user. Foraccess control system 22 a, typical events would be a user entry or exitthrough a door, unauthorized attempt to enter, or forced entry. For theintrusion detection system 22 b, typical events would be the detectionof an intrusion in a zone, and for a fire system 22 c, a typical eventwould be the detection of smoke or fire is a zone or area. For digitalvideo recording and surveillance system 22 d, a typical event would bethe detection of motion within the viewing area of a specific camera.Certain events at information systems 18 and facility protection systems22 indicating a security risk condition represent alarms at such system,and in integrated system 10 generally. Each of the systems 18 and 22internally is programmed to react to events, while also sending eventdata packets to the security server 12 describing the events.

The security server 12 receives each of the event data packets at anevent transaction processor 13 for determination of actions, if any, thesystem 10 will take, and, depending on the event received, sendingaction data packets automatically and in real-time to systems 18 and 22to take appropriate action. Actions may be based on occurrence of asingle event or multiple events at the same or different ones of systems18 and 22. The event data packets may further be sent to one or moremonitoring client systems 24 for monitoring of events. Action datapackets may also be sent to monitoring client systems 24 for monitoringsystem 10's response to actions. An illustration of the process insystem 10 for an event data packet transmitted from the access controlsystem 22 a to security server 12 is shown in FIG. 2, in which actiondata packets may be sent to each of the information systems 18 to causeactions to take place in such systems to protect information property,as shown in FIGS. 5A and 5B. The process in system 10 for an event datapacket transmitted from any one of information systems 18 to securityserver 12 is shown in FIG. 3, in which as a result, action data packetsmay be sent to facility protection systems 22 to cause actions to takeplace on such systems to protect physical property by limiting orlocking out a users to areas of a building, as shown in FIGS. 6A-6C withrespect to the access control system 22 a. Another action which may betaken by security server 12 is to call a preset pager number, atelephone number with an automated message, or e-mail address with amessage in response to specific event types via output devices 16.

In addition to events being received by the security server fromfacility protection systems 22 and information systems 18, events mayautomatically be generated by the security server, such as based on apredefined termination date of a user's access privileges, which whenread by the event transaction processor 13 causes actions to limit orremove access privileges by the user to facilities controlled by theaccess control system 18 a and information systems 18.

The information from the event data packets is also stored by thesecurity server 12 chronologically as a record in an event log in thecentral database 14. An event log record includes at least the time anddate, originator (i.e., System ID) of the event data packet, and datacontent describing the event. Unique codes may be used by securityserver 12 for different events from systems 18 or 22. As stated earlier,each event data packet is also sent by security server 12 to one or morealarm monitoring client systems 24 which enable real-time display ofevents to personnel, especially such events representing alarms. Thesecurity server 12 maintains in the central database a list of the IPaddresses of such client systems 24 to which event data packets arerouted. Alarm monitoring client systems 24 represent computerworkstations, computer systems, or other devices capable of receivingevent data, which can connect to security server 12 over the network, orreceive messages by e-mail, pager, or personal digital assistant, fromsecurity server 12, via output devices 16. Software applicationsoperating on such alarm-monitoring client system to enable display ofevents occurring in system 10 may be such, as used in the ONGUARD®system mentioned earlier.

The system 10 also includes an external database, shown as a HumanResource (HR) database 26 (or a directory, accessible through protocolssuch as LDAP), as described in the above-incorporated patentapplication, in which transactions in user data are sent to the securityserver 12 for storage in one or more tables of the central database 14.The HR database 26 may be memory of another computer server to enablecommunication with security server 12. HR database 26 is coupled to HRcomputer systems 28. Each time user information stored in HR database 26is changed (add, modify, or delete) by HR computer systems 28, atransaction defining the change is stored on the HR database. Thetransaction can be read by security server 12 and downloaded by theserver to map the changed user data from the HR database 26 to recordsin one or more user data tables of the central database 12, similar tothat described in the earlier incorporated patent application. Examplesof tables for integration of the access control system 22 a of thisincorporated application with other facility protection systems 22, andinformation systems 18, are described later below.

In response to receiving user data representing additions of a new userto system 10, security server 12 assigns a unique Internal ID forinternal management of users, and assigns security information, suchsecurity access privileges, in system 10 in facility protection system'sphysical environment of ACS 22 a, IDS 22 b, and to information systems18 data and network environment. For example, user data stored in thecentral database may include information regarding the type of user (oremployee type) as researcher, sales, contractor, or any other type thatmay characterize particular access privileges to areas of a building andtype of information. An access privileges lookup table in memory of thecentral database 14 associates user data, such as type of user and/ortime periods/shifts, to one of different access privileges in the accesscontrol system 22 a. Each access privilege characterizes the areas andtime of access to controlled areas of buildings. Such tables aredescribed in the incorporated patent application as Access Level LinkTable and Access Lenel Table. Similarly, the same access privilegeslook-up table, or a different look-up table, specifies which zones, ifany, of the IDS 22 b the user can mask. The same access privilegelook-up table, or a different look-up table in memory of the centraldatabase 14 associates user data, such as type of user, department, orlocation (building, city or state) to one or more of the informationsystems 18 the user should have access to. The access privileges infacility protection systems (22 a and 22 b) and information systems 18may change in accordance with updated user data received in transactionsfor the HR database 26.

As shown in FIGS. 2 and 3, if such action in response to an eventchanges user data stored on security server 12, in central database 14such change in user data may be sent to the HR database 26, such thatthe HR database is maintained current. Further, an administration system30 in FIG. 1, representing a computer system, is provided in system 10which can access the central database 14 in security server 12 to reviewand update information stored therein, such as update user data,security access privileges, or generate and manage badge ID cards, oraction ID Credentials, and also Login IDs, passwords, and other digitalcredentials, such as smart cards, security tokens, digital certificatesand biometric templates.

The central database 12 includes multiple tables for data management ofsystem 10. One such table is the User Table, as shown for example below.

USER TABLE Internal ID LastName FirstName MiddleName SSN Last ChangedAddress City State Zipcode Department Phone Building Title User TypeStatus Termination Date

Each user has a record in the User Table, referred to herein as a userrecord, which in the example shown above includes the following datafields: a unique Internal ID, assigned by system 10 for identifying eachuser; LastName, FirstName, and MiddleName for the parts of the user'sname; SSN is the user's social security number or other public uniqueidentifier for an individual; Last Changed is the date and time therecord was last changed; Address, City, State, and Zipcode, of theuser's work address; Department is the department or group the user isassociated with; Phone is the user's work phone number; Building is thebuilding where the user works; Title is the title of the user'sposition; user Type refers to the type of user as described earlier;Status may be active, non-active, or one of different types ofnon-active, such as medical or retired; and Termination Date, ifapplicable, may be used for term employees, such as contractors orseasonal workers. Other information stored in the fields of the usertable, may be such as described in the Employee table of U.S. patentapplication Ser. No. 09/135,822, filed Aug. 18, 1998, or as needed basedon the institution in which system 10 is used.

Another table in the central database 12 is the User-System-SecurityTable shown, for example, below.

USER-SYSTEM-SECURITY TABLE System ID Internal ID Login ID Password SIDStatus

The records in the User-System-Security Table stores for each user theiraccess privileges to information systems 18 in terms of whichinformation system the user has access to. In other words, for eachinformation system 18 the user has access to, a record exists in thistable having the System ID of the information system, the Internal ID ofthe user in system 10, and authorization information, Login ID andPassword, for the user to access their account on the informationsystem. Also stored in the table is a SID which represent a securityidentifier having a value unique to every account for a user in a givensystem, which reference the users for that system and their associatedauthorization information, i.e., Login ID and Password. For example,Domain Controllers for Windows NT Server 18 a, assigns a unique SID foreach user having an account on the system, and stores on its server 18(such as a database), records linking the SID to the Login ID andPassword, assigned to the user. Optionally, to avoid duplicating datafor such an information system 18 using SID's, the Login ID and Passwordfields in a record of the User-System-Security Table of that system maybe removed. In this case, if the Login ID and/or password of a user wereneeded by the security server 12, the server by a querying command in anaction data packet to the information system may obtain the Login IDand/or password for a SID. If an information system 18 does not use anSID, then that field in the User-System-Security Table need not be used.The User Table and the User-System-Security Table are relationallylinked by the Internal ID of the user.

When a new user is added in system 10, such as by the addition of userrecord in the User Table, the security server 12 automaticallydetermines which of the information system 18 the user should haveaccess to based on the lookup table described earlier which associatesuser data of the user record with one, several, or all of theinformation system 18, i.e., System ID of those information system(s)such a user should have access to. This is useful in assuring that onlyusers needing access to an information system are provided with suchaccess. For example, in a work environment where users are employees, anemployee in the Sales Department, would not need access to aninformation system used by employees in a Research and Development (R&D)Department, and an employee in an R&D Department would not need accessto an information system storing sales information. Alternatively, usersmay have access to all information systems 18 in system 10, and thus nouse of a look-up table to assign access privileges to information systemis needed. Although a look-up table is described, any rules may beprogrammed to associate information in one or more fields on User Tableand particular information systems 18.

Once the information systems 18 are identified for the new user, thesecurity server 12 adds a record to the User-System-Security Table foreach of such information system having the Internal ID of the user andthe System ID of the information system. The security server 12 for eachnew record in this table, automatically determines the Login ID andPassword in accordance with the authorization protocol of theinformation system associated with the record, stores the Login ID andPassword in the record, and sends a new account command in an actiondata packet over the network 20 to the information system to open a newuser account with that Login ID and password. For example, such Login IDand/or password may be based on combination of a user's first and lastname from the user record in the User Table data. The new accountcommand would also include any other information needed by theparticular information system for opening an account, such as name ofuser, department, and type of employee, location, or other informationin the user record in the User Table. Usually, the new account whenopened is assigned default privileges by the information system 18 toits resources, such as directories, files, documents, databases,programs, or network(s) maintained by such information system.Optionally, an information system 18 may use the information about theuser provided by the security server 12 to assign access privileges interms of which resources such user may access, or time of day orspecific terminals or computers access is to be made available. Suchassigned privileges by the information system is stored in eachrespective information system and can be accessed and modified by thesecurity server 12 via a query command in an action data packet withusing SIDs or Login ID. If the Login ID already exists for theinformation system when a new account command is received, theinformation system will not generate an account for the user, and willsend a message to the security server informing that the Login ID is inuse. In such a case, the security server 12 automatically, based on therules for that information system, generates a new Login ID, such as forexample, replacing or adding more letters or numbers to the previouslydetermined Login ID. The new Login ID is then stored in the record inthe record for the information system and user in theUser-System-Security Table, and a new account command is resent in anaction data packet to the information system to open a new user accountwith the password and new Login ID. Alternatively, the security server12 could defer to an information system 18 to provide the userauthorization information, in which the new account command in an actiondata packet would have information about the user from the user record,and the information system would return to the security server the userauthorization information (SID, or Login ID and Password) for storage ina record in the User-System-Security Table.

In response to opening a new account, the information system 18 returnsan SID and the security server 12 stores the SID in the record for theinformation system (System ID) and user (Internal ID) in theUser-System-Security Table. The return of an SID thus represents aconfirmation message that the new account is successfully opened. If theinformation system does not use SID's, a confirmation message is alsoreturned to the security server 12 indicating the new account issuccessfully opened having the Login ID of the user. The above isrepeated for each information system the new user will have access to.

If a user record in the User Table is changed (added, deleted, orupdated), and such changes may effect security access to informationsystems 18, especially if the user record is deleted, or fields of theuser record associated with access privileges, such as status oremployee type, have changed. Changes in user records effecting securityaccess are downloaded (distributed) to information systems. For example,if a user record were deleted, then all records for the user in theUser-System-Security Table will be deleted or have their Status fieldschanged to inactive, and the security server automatically sends adisable Login (or account) command in an action data packet to theSystem ID of information system of the effected records. Further, forexample, if in a user record fields associated with access privilegeswere changed, the security server using the look-up table providingaccess privilege association between user table fields and informationsystems, adds a new record in the User-System-Security Table for eachnew information system to which the user has access, such as describedearlier in opening a new user account, and changes the Status field toinactive for records in the User-System-Security Table for the user forany information system to which access privileges are no longerprovided, such as described earlier in disabling a user's Login.Sometimes, changes in the User Table records do not effect securityaccess, but represent information stored for the user's account in theinformation system, such as address or phone number, which may bedownloaded to an information system in an action data packet with theSID or Login ID of the user and an account update command with theupdated information.

Further, another table, Security-System-Table may be provide, such asshown for example below.

SYSTEM SECURITY TABLE System ID System Name Server Location Locations

For each information system 18 in system 10, the System Security Tablehas a record including fields: System ID of the information system;System Name of the information system of that System ID; Server Locationhaving as text or codes defining the particular facility where theinformation system's server is located; and Locations having text orcodes defining the site, building, rooms, or areas of a facility whereuse of the information system is authorized, such as where terminals orcomputers associated with the information system are located. This isuseful for associating the physical environment protected by facilityprotections systems with each information system.

The user's authorization information for the information systems 18typically has user authorization information of a Login ID and Password,needed to enable to the user to access the user's account on the system,such as described above. If other or additional digital ID Credentialsare needed for a particular information system, such may be stored inadditional field(s) in the record for the user to the information systemin the User-System-Security Table, or such fields may store thelocation, address, or filename, where such ID Credentials may be foundin memory (e.g., central database) of the security server, and storedtherein by a central system administration client 30. Such a client 30would have components or other means for obtaining such ID Credentialsinformation, such as digital certificates, fingerprint data, or otherbiometric information.

An information system 18 when first added to the system 10 and linked tothe security server 12 may have user accounts already established. If auser already has an account for a particular information system 18 whenthat information system is first added to system 10, then the SID forthe user is mapped to the user's Internal ID for storage in a record theUser-System-Security Table of the central database 14 having the SystemID of the information system. Similarly, other digital ID Credentialsmay be mapped, such as Login ID and Passwords.

Additional tables in the central database 14 store the users' badges orother user authenticity ID credential to gain entry/exit to areas offacilities controlled by the access control system 22 a. These table(s),including a Badge Table, is described in the earlier incorporated patentapplication.

Other tables may also be provided in the central database 14, dependingon the facility protection systems 22 in system 10. For example, eachuser having a personal safety device has a record in a Transmitter Tableincluding their Internal ID, and frequency, code, and/or identifier oftheir personal transmitter. For example, each of the assets beingmanaged has a record in an Asset Table including their unique Asset ID,and information describing the asset. Each user possessing a managedasset would have a record in an Asset Link Table, which includes theInternal ID of the user, and the Asset ID(s) of an Asset Group the usermay possess. The Asset Group refers to a list of Assets, i.e., AssetIDs, which may be grouped together.

The intrusion detection system 22 b may store a list of Internal IDs ofusers as codes enabling masking of zone at its control panels. Theaccess privileges look-up table in the central database 14 describedearlier can include information as to whether a user has masking accessprivilege and the extent of the zones to which the privilege in system22 b extends. At the same time, access to information systems 18 isbeing established, security server 12 may automatically download new orchanged security information to the access controllers of the accesscontrol system 22 a in accordance with the security privileges of theuser, such that a badge, or other personal credentials, such as abiometric template, may be used by the user to enter certain areas ofthe building at certain times, as described in the earlier incorporatedpatent application. Further, the security server 12 may automaticallydownload new or changed security information to the intrusion detectionsystem 22 b any zones the user will have the ability to mask fromdetection from the system in accordance with the security privileges ofthe user. The security server 12 can further download to informationsystems 18 new or changes in security data for each user based oninformation stored relevant to such security in the central database, asdescribed earlier. Thus, system 10 enables central control of accessprivileges to all systems 18 and 22. The distribution (download) ofsecurity information in system 10 is described in more detail below.

Referring to FIGS. 4A and 4B, a flow chart for the distribution ofsecurity information in system 10 in response to transactions read froma transaction table in the HR database 26 is shown. In these figures andFIGS. 5A,5B, and 6A-6C, IPS or IS refers to one of information systems18. The security server 12 first reads a transaction from the listqueued in the transaction table specifying the update (add, modify, ordelete) in the user data maintained in the HR database (step 32), andmaps the updated user data into records of one or more of the tables ofthe central database 14 (step 34). The user data provides informationabout a user such as stored in the User Table. The download and mappingof user data from the HR database 26 to the central database 14 of steps32 and 34 may be similar to that described in detail in the earlierincorporated patent application. Such mapping includes assigning thesecurity information, security access privileges for access controlsystem 22 a and to information systems 18 by building or updatingrecords in the User-System-Security-Table for information system theuser should have access to if either a new user is added, or the userdata is modified such that the security information for the user isaffected. For example, changing the user type may change their accessprivileges. The security server 12 checks if the transaction read wasmapped to the central database (step 36). If so, the HR database isupdated by removing the transaction from its transaction table (step40), otherwise, an error in either the central database, or in the userdata of the transaction, has occurred, and a copy of the transaction isstored in an error log of the central database 14 for review byadministrator system 30 (step 38).

Next, at step 42, changes in a user's security information stored in thecentral database affecting access privileges are transmitted to theaccess control system 22 a, intrusion detection system 22 b, andinformation systems 18. To send changes in security information for auser, an action data packet is sent to each affected system to effectthe user's account on the information system. The action data packetsent to network and information system 18 uses a command appropriate forthe interface of system 18 with the Login ID or SID in accordance withthe user's Internal ID in the User-System-Security Table. If no Login IDis present on the information system 18, one is generated as describedearlier with a default password. The action data packet transmitted tothe access control system 22 a uses a command appropriate for theinterface of the access control system with the Internal ID of the user.The transmission of the information in the action data packet for theaccess control system to add, modify, or delete security information,may be similar to that described in the earlier incorporated patentapplication.

The interface for each information system 18, access control system 22a, and intrusion detection system 22 b receives, formats, and sends thesecurity information to controllers of such systems to update thesecurity information for the system accordingly (step 44). In the caseof information system 18, such command may for example, direct thesystem to add a new user account, delete a user account, remove accessprivilege or block Login, for the Login ID or SID of the user. As statedearlier, if a new user is being added, the command may be to add newuser account, which include a security server generated Login ID andpassword, or the information system will return to the security server12, SID or the Login ID and password assigned for that system, forassociation with the User-System-Security Table. In the case of theaccess control system 22 a, the action data packet may be addressed bythe security server 12 to the access controller(s) affected having acommand for the Internal ID of the user. Further, for the intrusiondetection system 22 b, the controllers (control panels) of the systemmay be updated with respect to the Internal ID to mask zones monitoredby the system. The particular command and content of fields of the datastructure of the action data packet depends on the security informationchange for the user in the central database 14. The interface of theaccess control system 22 a, intrusion detection system 22 b, andinformation system 18 receive messages from the respective controllersindicating whether the security information was received and accepted(step 46), and transmits a response message from their respectivecontrollers to the security server 12 indicating such (step 48). Foreach access control system 22 a, intrusion detection system 22 b, andnetwork and information system 18, if the security server 12 receives amessage indicating that the security information was accepted by theinterface (step 50), the server 12 stores in an import log of thecentral database 14 an entry indicating that the download of securityinformation was successful (step 52). If the security information wasnot accepted, the security server 12 stores in a failed commands log ofthe central database 14 a copy of the information of the action datapacket sent to the system for review by personnel at administrationsystem 30 (step 54).

Referring to FIGS. 5A and 5B, the process of an event occurring at theaccess control system 22 a is shown. For example, events may be a badgeused at a card reader to access an area, or a “forced door open” toaccess an area. Starting at step 56, the event is first read (collected)by the software interface from memory of the access controller of system22 a. The software interface sends (routes) the event information in anevent data packet to the security server 12, which logs the event datapacket as an event transaction in the central database 14, and routesthe event transaction to alarm monitoring clients 24 and eventtransaction processor 13 (step 50). If the event transaction did not getlogged in the central database 14 (step 60), an error has occurred, anda copy of the event transaction is stored in a temporary file in thecentral database, until the central database 14 is available to log theevent transaction (step 62). If the event transaction did not get routedto alarm monitoring clients (step 64), an error is stored in the errorlog of the central database 14 with a copy of the event transaction(step 66). Each client returns a message to the security server 12indicating the event transaction was received. The security server 12determines that an event transaction was not routed to a client when nosuch message is returned from a client. If the event transaction did notget routed to the event transaction processor 13 (step 68), an error isstored in the error log of the central database 14 with a copy of theevent transaction (step 70). The security server 12 knows when an eventwas routed to the event transaction processor when it received an ACK(acknowledge) message from the processor. The event transactionprocessor 13 determines if any actions are needed at the informationsystems 18 in response to the event transaction from the access controlsystem 22 a (step 72). If so, the event transaction processor formatsaction data packets to direct information systems 18 to take appropriateactions (step 76), otherwise the event transaction is discarded by theevent transaction processor (step 74). The operation of the eventtransaction processor at steps 72, 74 and 76 are described in moredetail in connection with FIG. 7. Each of the interfaces of theinformation systems 18 receiving an action data packet, directs thecontroller of the information system 18 to operate in accordance withthe command and data of the action data packet, and sends a message backto the security server 12 indicating whether the action data packet wasaccepted. The security server 12 checks the received message for eachinformation system interface to determine if the action data packet wasaccepted (step 78). If so, the security server 12 updates a transactionlog in the central database 14 with a success status (step 82),otherwise, a copy of the sent action data packet is stored in thecentral database 14 for review by personnel at administrator system 30(step 80). Similarly, an event from any facility protection system 22may be processed in the same manner as described from access controlsystem 22 a, and cause actions at other facility protection systemsand/or information systems.

The actions taken by the information systems 18 to protect networks anddata resources sometimes needs to be made aware to HR personnel, suchthat they are aware of any changes in the status of the users and accessprivileges in the information system 18, or if needed, take appropriatecorrective action. For example, a badge used by a user to access areascontrolled by the access control system may have expired, causing anevent transaction which sends action data packets to information systems18 to block the user's Login ID. The security server 12 can check a listof such actions requiring HR notification stored in central database 14to determine if the action affects HR (step 84). If so, the businessrules for the affected data are looked up, such as in a table of thecentral database 14 (step 88 a) and then the security server 12 check ifit needs to be applied (step 88 b). Business rules represent when theaction taken requires that data stored in the HR system's database bechanged. If no business rules are found, or if the business rules foundrequire only that notification be provided, the no branch from step 88 bis taken to step 90 to send an update transaction to the HR system tonotify personnel in HR, such as in a log. If the business rules need tobe applied at step 88 b, the business rules are applied for the HRsystem to send an update transaction that both provides notification andupdates the appropriate record in the HR database for the user affectedat step 90. The HR database 26 sends a message to the security server 12if the HR database was successfully updated. If so, the transaction islogged in the transaction log of the central database 14 (step 96),otherwise, an error is added to the error log of the central database 14with a copy of the update transaction sent (step 94).

Referring to FIGS. 6A-6C, the process of an event occurring at one ofthe information systems 18 is shown. For example, an event may be anetwork intrusion detection such as by Windows NT Server 18 a at aterminal located within a particular building. Starting at step 98, theevent is first read by the software interface from memory of theinformation system 18 storing the event. The interface sends (routes)the event information in an event data packet to the security server 12,which logs the event data packet as an event transaction in the centraldatabase 14, and routes the event transaction to alarm monitoringclients 24 and event transaction processor 13 (step 100). If the eventtransaction was not logged in the central database 14 (step 102), anerror has occurred, and a copy of the event transaction is stored in atemporary file in the central database, until the central database 14 isavailable to log the transaction (step 104). If the event transactionwas not routed to any alarm monitoring clients (step 106), an error isstored in the error log of the central database 14 with a copy of theevent transaction (step 108). If the event transaction did not getrouted to the global event transaction processor 13 (step 110), an erroris stored in the error log of the central database 14 with a copy of theevent transaction (step 112). The event transaction processor 13determines if any actions are needed at the access control system 22 a(step 114). If so, the event transaction processor 13 formats actiondata packets to direct the access control systems 22 a to takeappropriate actions (step 118), otherwise the event transaction isdiscarded by the event transaction processor (step 122). The operationof the global event transaction processor at step 114, 116, and 118 aredescribed later in more detail in connection with FIG. 7. The softwareinterface of the access control system 22 a receives the action datapacket to direct the access controller of the access control system 22 ato operate according to the command and data of the action data packet,and sends a message back to the security server 12 indicating whetherthe action data packet was accepted. The security server 12 checks thereceived message to determine if the action data packet was accepted(step 120). If so, the security server 12 updates a transaction log inthe central database 14 with a success status (step 124), otherwise, acopy of the sent action data packet is stored in the central database 14for review by administrator system 30 (step 122). If actions local tothe information system are also needed in addition to sending an eventto the security server 12, the information system may operate to blockaccess for a Login ID, as typical network security systems provide whenpossible intrusion is detected for a Login ID. Reference at steps114-122 to actions by access control system 22 a, are exemplary, any ofthe facility protection systems 22 or other information systems 18 maybe directed to take an action.

Internally, the security server 12 identifies each user by theirInternal ID. When sending action data packets to network and informationsystem 18, the security server 12 used the Login ID or SID associatedwith the Internal ID in the User-System-Security Table. The accesscontrol system 22 a may use the Badge ID rather than the Internal ID toidentify different badges, which may be provided in another table linkedto the User Table by the Internal ID. If so, when sending action datapackets to access control system 22 a, the security server 12 uses theUser Table to associate the Internal ID with the Badge ID assigned tothe user to identify the user to the access control system.

Referring to FIG. 6C, as with actions taken by the information systems18 to protect network and data resources, actions affecting users accessto areas of building sometimes need to be made aware to HR personnel,such that appropriate corrective action may be taken. To determinewhether the access control system action affects the HR system, thesecurity server 12 checks a list of such actions requiring HRnotification stored in central database 14 to determine whether the userdata stored in the HR database is affected (i.e., changed) by the action(step 126). If so, the business rules for the affected data are lookedup, such as in a table of the central database 14 (step 130) and thenthe security server 12 check if it needs to be applied (step 131). If nobusiness rules are found, or if the business rules found require onlythat notification be provided, the no branch from step 131 is taken tostep 133 to send an update transaction to the HR system to notifypersonnel in HR, such as in a log. If the business rules need to beapplied at step 131, the business rules are applied for the HR system tosend an update transaction that both provides notification and updatesthe appropriate record in the HR database for the user affected at step133. For example, an action may be to deactivate the badge of a user atthe access control system 22 a. In this case, a record for the HR systemfor the user would then be updated indicating the badge was deactivated.In this manner, the HR records will be maintained current for users. TheHR database 26 sends a message to the security server 12 if the HRdatabase was successfully updated (step 134). If so, the transaction islogged in the transaction log of the central database 14 (step 138),otherwise, an error is added to the error log of the central database 14with a copy of the update transaction sent (step 136).

Referring to FIG. 7, a flow chart showing the process and programming ofthe event transaction processor 13 of security server 12 is shown. Atstep 140, an event data packet is received from one of the informationsystems 18 and facility protection systems 22 having information for anevent transaction in system 10. The originator's System ID, time anddate of the event, location of the event, and an event code, (InternalID and/or a Login ID or SID), if the event relates to a particular user,is read from the event transaction. The date and time of the event maybe in data fields of a received event data packet, or the date and timethe event data packet was received by the security server 12, inaccordance with the time and date of the clock of security server 12.Based on the event code and originator of the event, security server 12searches for a matching entry in a record of a Rules Table matching theevent code and originator's System ID. Each entry has data with anyactions to be taken by system 10. If no record is found, or no actionsare indicated, the event transaction is discarded (step 147) and theprocess ends (step 156). If one or more actions are found for thatentry, the security server 12 locates such actions (step 148) in theRules Table and for each recipient of the action, an action data packetis prepared (steps 150). The Rules Table may include the command anddata structure for fields needed for the particular software interfaceof the recipient of the action data packet. The action data packets arethen sent to the recipient systems (step 152) and logged in centraldatabase 14 (step 154), and the process ends at step 156. The datastructure for locating and applying rules of the Rules Table isexemplary. Other data structures may be used to check if a rule for anevent transaction exists and the actions needed in system 10. Forexample, a structure of if-then conditions may be used based on thesender System ID, the system type (22 a to 22 d or 18 a-18 d) of thesender System ID, an event code for the transaction which occurred, andthe target System ID(s) to be affected in response to the event. Theparticular actions at systems in response to an events at another systemdepends on the specific event, and as such, the event transactionprocessor may be programmed accordingly to provide the desired responsewhich promotes security in the overall system 10.

Examples of event and corresponding actions in system 10 follow. Accesscontrol system event: an access control system 22 a deactivating a badgeof a user—action: block Login ID for the user at information systems 18.Access control system event: access control system 22 a detects doorforced open in an area—action: disable all terminals, PCs andworkstations protected by information systems 18 in area where door wasforced open. Fire system event: fire/smoke in a zone—action: backup datafor all information systems in area associated with a zone or switchcontrol to alternate network servers which may be located in a facility.Information system event: network intrusion detection of unauthorizedaccess at a terminal in an area—action: access control system 22 a locksdoor(s) in area to block exit by intruder. Information system event:information system 18 detects unauthorized login attempt after businesshours—action: create alarm in access control system 22 a, activate badgeusage trace in access control system 22 a at every card reader in thearea where the unauthorized login attempt occurred, close perimeterdoors to the area, activate video camera of digital video system 22 d inthe area and start recording and surveillance. (The digital video cameracan record events in an area where an event indicating a security riskis detected, such that undisputable evidence of the event and personsinvolved may be obtained.) Intrusion detection event: movement sensed ina zone of a building by intrusion detection system 22 b-action: accesscontrol system 22 a lock door(s) in area associated with the zone toblock exit by possible intruder, and secures (disables) terminals orcomputer to any information systems in the building area associated withthe zone. Fire event: detection of fire/smoke in zone of the buildingsfrom a fire system 22 c-action: information control systems 18 having aserver location in the area associated with the zone (as stored in thesecurity system table records) immediately backups data from its serversto another location in an area of the building or another building tominimize risk of damage. Digital video event: digital video system 22 dindicates movement in a scene when no users have entered the area—accesscontrol system 22 a lock door(s) in area where video is taken to blockexit. Information system event: user logs into a terminal—action:capture digital video or image by digital video recording andsurveillance system 22 d if camera in area where terminal is located.Asset management event: physical asset detected as moved through a door,by asset management system and Asset ID of the asset is not associatedwith Internal ID of User's badge used at reader to open door—action:activate digital video camera in area where asset is located to recordscene, and access control system 22 a lock doors in area to block exitby an unauthorized person.

Thus, system 10 integrates security to the physical environment providedby the access control system, and also building protection systems, withsecurity to network and data environment provided by information systems18, such that actions to events occur automatically and in real-time.The zones or area used by the facility protection systems 22 areassociated by the event transaction processor 13 with one or more areascontrolled by computers or terminals associated with information systems18, using the location field in the record in the security system tablefor the information system, such that actions taken can be specific tothe area of possible security risk. These events and actions areexemplary, other events typical of information systems 18 and facilityprotection systems 22 may cause different actions at other informationsystems 18 or facility protection systems 22 depending on the nature ofthe event.

Although the above describes the operation of the event transactionprocessor 13 to a single event, the event transaction processor maycheck whether the occurrence of multiple events requires action(s) insystem 10. This may be achieved logging each event read at step 142 in amultiple event transaction log in memory of the central database 14.Preferably, only events which have event codes and System ID which matchthose stored on a look-up-table in the central database of possibleevents which could be combined with other event(s) to require action insystem 10. The event transaction processor 13 operates similar to steps144-156, each time an event is added to the multiple event transactionlog, so as to locate rule(s) for any combination of events in themultiple events transaction log to determine if action is needed, and tolocate, prepare, and send action data packets to effect such actionsassociated with each of the applicable rules. The action(s) are loggedin the central database. The check for multiple events is done by theevent transaction processor 13 in parallel with a check for singleevent, or may be done by another one of event transaction processor 13in the security server 12.

The system 10 may optionally enhance security by maintaining useraccounts at one or more information systems 18 in a disabled Loginstate. When an event is received by the event transaction processor 13from the access control system 18 a that a user has entered a location,such as a facility site, area, building, a room, (e.g., by use of badgeat a reader of the access control system 18 a) the event transactionprocessor applies a rule that if the location matches one or moreauthorized locations for use of the information system, as stored in arecord in the System Security Table, for the information system, theuser's Login for the information system is enabled. Similarly, when theevent transaction processor 13 receives an event that the same user hasexited the location, the user's Login for the information system isagain disabled. Security may be further enhanced by requiring two eventsto occur at the event transaction processor 13, entry into an authorizedlocation by the access control system 22 a and detection at a motionsensor of the IDS 22 b in the area where the terminal or computer forthe information system is located in that area. An additional thirdevent, or instead of the IDS event, may also be used if a digital videocamera of the digital video recording and surveillance system 22 d werelocated in such area where the information system terminal was located.Thus, access in the physical environment is required for access to thenetwork and data environment of an information system.

From the foregoing description, it will be apparent that there has beenprovided a system and method for integrating security and access forfacilities and information systems. Variations and modifications in theherein described system and method in accordance with the invention willundoubtedly suggest themselves to those skilled in the art. Accordingly,the foregoing description should be taken as illustrative and not in alimiting sense.

1. A security system for integrating security and access for facilityprotection systems and information systems in which each informationsystem represents a computer system requiring user authorization atconnected computers or terminals to access information resources ornetwork environment protected by the information system, said securitysystem comprising: a computer system coupled for communication with oneor more facility protection systems and one or more information systems,in which said computer system has memory storing at least user data andaccess privileges of users to said one or more information systems andsaid one or more facility protection systems, and said access privilegesare capable of being assigned or updated when the user data is added,modified, or deleted in said memory; and said computer system beingcapable of receiving event data from said one or more facilityprotection systems and said one or more information systems, and beingoperative to send action data in accordance with one or more of saidreceived events for directing said one or more facility protectionsystems or said one or more information system to take one or moreactions.
 2. The system according to claim 1 wherein said one or moreinformation systems are capable of being directed to take one or moreactions in accordance with one or more said received events from atleast one of said one or more facility protection systems.
 3. The systemaccording to claim 1 wherein at least one of said one or more facilityprotection systems controls user access to areas of a facility, and saidaccess privileges for each of the users comprises at least authorizationinformation for access to said one or more of said information systems,and information representing one of different levels of access to saidareas of the facility.
 4. The system according to claim 1 wherein saiduser data comprises information characterizing at least each of saidusers as being one of different types, in which said access privilegesof each of the users are in accordance with said user data of the user.5. The system according to claim 1 wherein at least one of said one ormore facility protection systems controls user access to areas of afacility, and other of said facility protection systems comprise one ormore of an intrusion detection system, a fire system, a buildingautomation system, a personal safety system, or a digital videorecording and surveillance system.
 6. The system according to claim 1wherein said facility protection systems comprise at least an accesscontrol system which controls user access to areas of a facility.
 7. Thesystem according to claim 6 wherein said access control system comprisesone or more readers for reading ID credentials associated with each ofthe users to obtain information uniquely associated with each of theusers, said access privileges of the users are associated with theinformation of each of the users, and said user data stored in memory ofsaid computer system are not added, modified or deleted when saidinformation is read by said one or more readers.
 8. The system accordingto claim 7 wherein said ID credentials represent one or more of badges,smart cards, tokens, or biometric information.
 9. The system accordingto claim 7 wherein said information for each of said ID credentialsrepresents at least an identifier uniquely associated with the user ofthe ID credential.
 10. A method for integrating security and access forat least one facility protection system and at least one informationsystem comprising the steps of: providing a computer system coupled forcommunication with said facility protection system and said informationsystem in which said computer system has memory storing at least userdata and access privileges of users to said information system and saidfacility protection system; assigning or updating the access privilegesin said memory when the user data is added, modified, or deleted in saidmemory; sending to said computer system one or more events from one ormore of said facility protection system and said information system; andsending one or more actions from said computer system to one or more ofsaid facility protection system and said information system inaccordance with one or more of said events for directing said one ormore of said facility protection system and said information system totake one or more actions.
 11. The method according to claim 10 whereinsaid facility protection system represents an access control systemwhich controls user access to areas of a facility.
 12. The methodaccording to claim 11 wherein said access control system comprises oneor more readers, and said method further comprises: reading IDcredentials associated with each of the users by said one or morereaders to obtain information uniquely associated with each of theusers, said access privileges of the users are associated with theinformation of each of the users, and said user data stored in memory ofsaid computer system are not added, modified or deleted when saidinformation is read by said one or more readers.
 13. The methodaccording to claim 10 wherein said facility protection system representsone of a plurality of facility protection systems.
 14. The methodaccording to claim 13 wherein at least one of said plurality of facilityprotection systems controls user access to areas of a facility, andother of said facility protection systems comprise one or more of anintrusion detection system, a fire system, a building automation system,a personal safety system, or a digital video recording and surveillancesystem.
 15. The method according to claim 10 wherein said informationsystem represents a computer system requiring user authorization atconnected computers or terminals to access information resources ornetwork environment protected by the information system.
 16. The methodaccording to claim 10 wherein said information system represents one ofa plurality of information systems.